Systems and methods for providing a collaboration work management platform that facilitates differentiation between users in an overarching group and one or more subsets of individual users

ABSTRACT

Systems and methods for providing a collaboration work management platform that facilitates differentiation between users in an overarching group and one or more subsets of individual users within the overarching group to enable the users within the individual subsets to use the collaboration work management platform differently users within the other subsets, the method being implemented by a computer system including one or more physical processors configured by machine-readable instructions are disclosed. Exemplary implementations may: manage environment state information for maintaining a collaboration environment.

FIELD OF THE DISCLOSURE

The present disclosure relates to systems and methods for providing acollaboration work management platform that facilitates differentiationbetween users in an overarching group and one or more subsets ofindividual users within the overarching group to enable the users withinthe individual subsets to use the collaboration work management platformdifferently from users within the other subsets.

BACKGROUND

Typical work management platforms have paid subscriptions and freesubscriptions. In existing collaborative platforms, if some users wantpremium features that come with the paid subscription, all users withinthe same organization have to pay to upgrade their subscription becausethe data structure does not enable sub-groups within companies to havedifferent types of accounts (e.g., some paid, some not) that providedifferent features. Providing premium features on an “organization”level only is not workable for a bottom up enterprise sales approach,because it requires a commitment to buy all register users across alarge organization. However, buying a single “team” offers too limitedfunctionality to satisfy the needs of divisional or departmental levelbuyers. These buyers, as a reflection of their purview, need to buy acollection of teams. Without a robust data structure accounting forgroups and subgroups, this isn't possible.

SUMMARY

One feature of the present disclosure includes systems and methods forproviding a collaboration work management platform that facilitatesdifferentiation between users in an overarching group and one or moresubsets of individual users within the overarching group to enable theusers within the individual subsets to use the collaboration workmanagement platform differently users within the other subsets.Functionality may be effectuated by establishing a data structure thatdifferentiates between users in an overarching group and one or moresubsets of individual users within the overarching group. In previouslyexisting work management systems and methods there was a limited set ofcapabilities for organizations that have different subsets of users.Typically, in existing systems, access to features, account types,layout, options, permissions, content, functionality, and/or otherdifferentiating aspects of work management systems but be differentiatedon an entire organization level, or on a user-by-user basis. A datastructure that differentiates between users in an overarching group andone or more subsets of individual users within the overarching group mayfacilitate differentiation between subsets of users. By way ofnon-limiting example, individual subsets of users may have differenttypes of accounts among users within an organization (e.g., some premiumaccounts and some non-premium accounts), different layouts or options,different permissions, different customizations, different content,different functionality, and/or other different features or differentways in which the users in individual subsets may use the managementplatform. The solution described herein creates another layer within thedata structure, a “middle layer” option (e.g., subsets), for thesesituations. A data structure having “group” and “subset” divisions mayallow a wider deployment different functionality.

One aspect of the present disclosure relates to a system configured forproviding a collaboration work management platform that facilitatesdifferentiation between users in an overarching group and one or moresubsets of individual users within the overarching group to enable theusers within the individual subsets to use the collaboration workmanagement platform differently users within the other subsets. Thesystem may include one or more hardware processors configured bymachine-readable instructions. The system may include one or moreservers, one or more client computing platforms, and/or othercomponents. The one or more servers may be configured to communicatewith one or more client computing platforms according to a client/serverarchitecture and/or other architecture. The one or more hardwareprocessors may be configured by machine-readable instructions to executeone or more computer program components. The computer program componentsmay include one or more of an environment state component, apresentation component, a features component, and/or other components.

The environment state component may be configured to manage environmentstate information for maintaining a collaboration environment. Theenvironment state information may include user records and work unitrecords. The environment state information may define a state of thecollaboration environment including a user state and a work unit state.The user state may be defined by the user records that define values ofuser parameters associated with users interacting with and/or viewingthe collaboration environment. The work unit state may be defined by thework unit records that define values of work unit parameters for unitsof work managed, created, and/or assigned within the collaborationenvironment.

The user parameters may include a group parameter identifying theoverarching group to which a first set of users, including a first user,belong such that a first user record for the first user defines a firstgroup value of the group parameter indicating the overarching group. Anoverarching group may be a high-level group within an entity that mayrepresent the entity and/or a division of the entity as a whole. Anoverarching group may include one of more of an organization, a company,an entity, a corporation, an enterprise, a business, and/or anotheroverarching group.

The user parameters may include a subset parameter denoting one or moresubsets within an overarching group to which one or more users withinthe first set of users belongs such that the first user record for thefirst user defines a first subset value of the subset parameterindicating a first subset within the overarching group to which a firstsubset of users including the first user belong. The subset may includeone or more teams, sub-groups, divisions, departments, task forces,and/or other subsets. In some implementations individual subsets mayinclude multiple groups of users (e.g., smaller than the overarchinggroup). By way of non-limiting example, the multiple groups of userswithin a subset may include multiple teams.

The processor(s) may be configured to effectuate presentation of thecollaboration environment for the collaboration work management platformbased on the environment state information including the user recordsand the work unit records.

These and other features, and characteristics of the present technology,as well as the methods of operation and functions of the relatedelements of structure and the combination of parts and economies ofmanufacture, will become more apparent upon consideration of thefollowing description and the appended claims with reference to theaccompanying drawings, all of which form a part of this specification,wherein like reference numerals designate corresponding parts in thevarious figures. It is to be expressly understood, however, that thedrawings are for the purpose of illustration and description only andare not intended as a definition of the limits of the invention. As usedin the specification and in the claims, the singular form of “a”, “an”,and “the” include plural referents unless the context clearly dictatesotherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system configured for providing a collaborationwork management platform that facilitates differentiation between usersin an overarching group and one or more subsets of individual userswithin the overarching group to enable the users within the individualsubsets to use the collaboration work management platform differentlyfrom users within the other subsets, in accordance with one or moreimplementations.

FIG. 2 illustrates an example overarching group and subset configurationas indicated by a group parameter and a subset parameter, in accordancewith one or more implementations.

FIG. 3 illustrates a method for providing a collaboration workmanagement platform that facilitates differentiation between users in anoverarching group and one or more subsets of individual users within theoverarching group to enable the users within the individual subsets touse the collaboration work management platform differently users withinthe other subsets, in accordance with one or more implementations.

FIG. 4 illustrates a method for providing a collaboration workmanagement platform that facilitates differentiation between users in anoverarching group and one or more subsets of individual users within theoverarching group to enable the users within the individual subsets touse the collaboration work management platform differently users withinthe other subsets, in accordance with one or more implementations.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 configured for providing a collaborationwork management platform that facilitates differentiation between usersin an overarching group and one or more subsets of individual userswithin the overarching group to enable the users within the individualsubsets to use the collaboration work management platform differentlyusers within the other subsets, in accordance with one or moreimplementations. In some implementations, system 100 may include one ormore servers 102. Server(s) 102 may be configured to communicate withone or more client computing platforms 104 according to a client/serverarchitecture and/or other architectures. Client computing platform(s)104 may be configured to communicate with other client computingplatforms via server(s) 102 and/or according to a peer-to-peerarchitecture and/or other architectures. Users may access system 100 viaclient computing platform(s) 104.

Server(s) 102 may be configured by machine-readable instructions 106.Machine-readable instructions 106 may include one or more instructioncomponents. The instruction components may include computer programcomponents. The instruction components may include one or more of anenvironment state component 108, a presentation component 110, afeatures component 112, and/or other instruction components.

Environment state component 108 may be configured to manage environmentstate information to maintain a collaboration environment. Theenvironment state information may include user records and work unitrecords. The environment state information may define a state of thecollaboration environment including user states, work unit states,and/or other states. The user states may be defined by the user recordsthat define values of user parameters associated with users interactingwith and/or viewing the collaboration environment. Individual ones ofthe user records may correspond to individual ones of the users. Thework unit states may be defined by the work unit records that definevalues of work unit parameters for units of work managed, created,and/or assigned within the collaboration environment. Individual ones ofthe work unit records may correspond to individual ones of the units ofwork and/or be associated with one or more users and/or other units ofwork.

The environment state information may include user records, work unitrecords, and/or other records. The environment state information may becontinuously generated and/or updated based on the state of thecollaboration environment representing the users' interactions with thecollaboration environment. The state of the collaboration environmentmay include a user state, a work unit state, and/or other states. Theuser state may be defined by the user records. The user records maydefine values of user parameters associated with users interacting withand/or viewing the collaboration environment. The work unit state may bedefined by the work unit records. The work unit records may definevalues of work unit parameters for units of work managed, created,and/or assigned within the collaboration environment. In someimplementations, the work unit state may include a project state, a taskstate, a sub-task state, and/or other states. The work unit records mayinclude project records, task records, sub-task records, and/or otherrecords.

The work unit parameters for work units managed, created, and/orassigned within the collaboration environment may include parametersdescribing one or more work units managed, created, and/or assignedwithin the collaboration environment and/or via the collaboration workmanagement platform, and/or the metadata associated with the one or morework units. Individual ones of the work units may be associated withindividual ones of the work unit records. A work unit record may definevalues of the work unit parameters associated with a given work unitmanaged, created, and/or assigned within the collaboration environmentand/or via the collaboration work management platform. A given work unitmay have one or more owners and/or one or more team members working onthe given work unit. Work units may include one or more to-do items,action items, objectives, and/or other units of work one or more usersshould accomplish and/or plan on accomplishing. Units of work may becreated by a given user for the given user and/or created by the givenuser and assigned to one or more other users. A given work unit mayinclude one or more projects, tasks, sub-tasks, and/or other units ofwork possibly assigned to and/or associated with one or more users.

The work unit parameters may, by way of non-limiting example, includeone or more of: one or more units of work, one or more user commentparameters (e.g., a creator, a recipient, one or more followers, one ormore other interested parties, content, one or more times, up-votes,other hard-coded responses, etc.), a work unit name, a work unitdescription, one or more work unit dates (e.g., a start date, a duedate, a completion date, and/or other work unit dates), one or moremembers associated with a unit of work (e.g., an owner, one or moreother project/task members, member access information, and/or other workunit members and/or member information), a status and/or progress (e.g.,an update, a hardcoded status update, a measured status, quantity ofwork units remaining in a given project, completed work units in a givenproject, and/or other status parameter), one or more attachments,notification settings, privacy, an associated URL, one or moreinteraction parameters (e.g., sources of the interactions, context ofthe interactions, content of the interactions, time for theinteractions, and/or other interaction parameters), updates, ordering ofunits of work within a given unit of work (e.g., tasks within a project,sub-tasks within a task, etc.,), state of a workspace for a given unitof work (e.g., application state parameters, application status,application interactions, user information, and/or other parametersrelated to the state of the workspace for a unit of work), dependenciesbetween one or more work units, one or more custom fields (e.g.,priority, cost, stage, and/or other custom fields), other work unitparameters for the given work units, and/or other work unit parameters,and/or user parameters for one or more users and/or work units the givenproject is associated with.

The user parameters associated with the users interacting with and/orviewing the collaboration environment may include parameters describingthe users, their actions within the collaboration environment, theirsettings, and/or other user information; and/or metadata associated withthe users, their actions within the environment, their settings, and/orother user information. Individual ones of the users may be associatedwith individual ones of the user records. A user record may definevalues of the user parameters associated with a given user interactingwith and/or viewing the collaboration environment.

The user parameters may, by way of non-limiting example, include one ormore of: a user name, a group parameter, a subset parameter, a useraccount, a user role, a user department, descriptive user content, ato-email, a from-email, a photo, an organization, a workspace, one ormore projects (which may include project parameters defined by one ormore work unit records), one or more items of work (which may includeone or more unit of work parameters defined by one or more unit of workrecords), one or more user comments, one or more teams the user belongsto, one or more of the user display settings (e.g., colors, size,project order, task order, other work unit order, etc.), one or moreauthorized applications, one or more presence/interaction parameters(e.g., indicating presence and/or interaction level at an environmentlevel, work unit level, project level, task level, application level,etc.), one or more notification settings, one or more progressparameters, status information for one or more work units the user isassociated with, one or more statistics related to a given user (e.g.,how many units of work the user has completed, how quickly the usercompleted the units of work, how quickly the user completes certaintypes of work units, the efficiency of the user, bandwidth of the user,activity level of the user, etc.), application access information (e.g.,username/password for one or more third-party applications), one or morefavorites and/or priorities, other user parameters for the given user,and/or other user parameters and/or work unit parameters, for one ormore work units the given user is associated with.

The user parameters may include a group parameter identifying theoverarching group. A first set of users, including a first user, maybelong to the overarching group. As such, a first user record for thefirst user may define a first group value of the group parameterindicating the overarching group. An overarching group may be ahigh-level group within an entity that may represent the entity and/or adivision of the entity as a whole (e.g., at the “org” or “organizationlevel”). An overarching group may include one of more of anorganization, a company, an entity, a corporation, an enterprise, abusiness, and/or another overarching group. An overarching group maycomprise an organized group of users and/or other entities with aparticular purpose (e.g., business, work, education, that engage inbusiness and/or work together toward a common goal.

The user parameters may include a subset parameter denoting one or moresubsets within an overarching group. One or more one or more userswithin the first set of users may belong to one or more subsets. Thefirst user record for the first user may define a first subset value ofthe subset parameter indicating a first subset within the overarchinggroup to which a first subset of users, including the first user,belong. A subset may include a sub-group of users and/or groups of userswithin the overarching group. A subset may be any group or groups ofusers smaller than the overarching group and/or within the overarchinggroup. The subsets may be system specific and/or correspond tosub-groups existing within a company (e.g., teams, departments,divisions, etc.). The subsets may include one or more of a team, asub-group, a division, a department, a task force, and/or other subset.In some implementations individual subsets may include multiple groupsof users (e.g., smaller than the overarching group). By way ofnon-limiting example, the multiple groups of users within a subset mayinclude multiple teams. By way of non-limiting example, a given user maybelong to one or more of the multiple teams such that a given userbelonging to a given subset may belong to multiple teams within thegiven subset. A subset division in the data structure may enable usersbelonging to multiple teams within a given subset to have premiumfeatures (e.g., first level features) for the multiple ones of the teamsincluded in the subset.

The user parameters may include a user account parameter. The users mayhave user accounts. Individual ones of the user accounts may havedifferent account levels. The account levels may indicate whether or nota user has a subscription level account (e.g., a premium level account,an executive account, a corporate account, etc.), a basic account, afree account, guest accounts, and/or other account levels. Differentsubsets of users may have different levels of accounts. For example, theusers belonging to the first subset may have first level accounts. Firstlevel accounts may include subscription level accounts. By way ofexample, the users belonging to the overarching group but not within thefirst subset may have second level accounts and/or other level accounts(besides first level accounts). Second level accounts may be basic,free, and/or guest accounts. The level of a given user's account maydictate which features the given user has access to within thecollaboration environment.

It is noted that any metadata and/or values of parameters related to anyusers, units of work, projects, tasks, subtasks, and/or other units ofwork may be considered values of user parameters and/or work unitparameters. The terms “user parameters” and/or “work unit parameters”may be used interchangeably herein.

FIG. 2 illustrates an example overarching group and subset configurationas indicated by a group parameter and a subset parameter, in accordancewith one or more implementations. Overarching group 201 may include oneor more subsets 203. Subsets 203 may include one or more teams 205.Teams 205 may include one or more users 207. Users 207 within a giventeam 205 and within a given subset 203 may belong to both the givensubset 203 and overarching group 201. For example, a user record foruser A 207A may define a first team value for the team parameterindicting team A 205A. The user record for user A 207A may define afirst group value of the group parameter indicating overarching group201, and/or a first subset value of the subset parameter indicatingsubset A 203A. Subset B 203B may be premium level subset including TeamD 205D and Team E 205E. User accounts for User H 207H, User I 207I, UserJ 207J, User K 207K, and User L 207L may be first level accounts. SubsetA 203A may be a second level subset such that user accounts for User E204E, User F 204F, and User G 204G may be second level accounts (and/orother level accounts besides first level accounts). User A 207A, User B207B, User C 207C, User D 207D, User E 207E, User F 207F, and User G207G may have second level accounts. User H 207H, User I 207I, User J207J, User K 207K, and User L 207L may have access to one or more firstlevel features. User A 207A, User B 207B, User C 207C, User D 207D, UserE 207E, User F 207F, and User G 207G may be restricted from accessingthe first level features.

In some implementations, User A 207A, User B 207B, User C 207C, User D207D, User E 207E, User F 207F, and/or User G 207G may have access toone or more first level features while they collaborate and/or interactwith one or more of User H 207H, User I 207I, User J 207J, User K 207K,and User L 207L. By way of non-limiting example, if User K 207K assignsa unit of work to User G 207G, User G 207G may have access to one ormore first level features while working on the unit of work.

Returning to FIG. 1 , presentation component 110 may be configured toeffectuate presentation of the collaboration environment for thecollaboration work management platform based on the environment stateinformation including the user records and the work unit records.Presentation of the collaboration environment may be based onenvironment state information. The collaboration environment may bepresented via individual client computing platform(s) 104 through whichthe users access the collaboration environment. The collaborationenvironment may include a one or more graphical user interfaces forpresenting work information (e.g., for units of work associated withusers) to the users, assigning units of work, managing units of work,organizing units of work, facilitating communication between the users,facilitating collaboration between the users, and/or otherwisefacilitating a collaboration work management platform.

Features component 112 may be configured to provide access to and/orrestrict access to first level features for the users within thecollaboration work management platform. Access may be provided and/orrestricted based on whether or not the users belong to both theoverarching group and the first subset of users. Features component 112may be configured to determine whether or not the users belong to boththe overarching group and the first subset of users, and/or whichsubset(s) the user's belong to. In some implementations, responsive to auser belonging to a first subset and the first overarching affiliation,they may be approved and/or able to register for a first level account.

In some implementations, access to a first level feature may be providedto the first subset of users based on the first subset of usersbelonging to both the overarching group and the first subset. In someimplementations, access to a first level feature may be restricted for asecond subset of users based on the second subset of users belonging tothe overarching group but not to the first subset. In someimplementations, access to first level features within the collaborationwork management platform may be provided to the first subset of users.First level features may include one or more of a type of account, alayout, one or more options, one or more permissions, a givenfunctionality, one or more customizations, a type and/or specificcontent, and/or other different features or different ways in which theusers in individual subsets may use the management platform.

By way of non-limiting example, users belonging to the first subset andthe overarching group may have access to a premium account, a givenplatform layouts, a given access point (e.g., mobile access), a givenoption (e.g., to interact with external users, to view a timeline and/ordashboard, to view statistics related to the platform, etc.), differentpermissions (e.g., to add and/or remove new users, to create and/ordelete projects, etc.), different customizations (e.g., a given homepageview, a color scheme, one or more application plug ins, etc.), differentcontent (e.g., content relevant to that subset), different functionality(e.g., given management type functions, etc.) and/or other differentfeatures or different ways in which the users in individual subsets mayuse the management platform.

In some implementations, first level features may include one or morepremium features. By way of non-limiting example, the first levelfeatures may include one or more of custom work unit templates (e.g.,custom templates for creating units of work), external invitecapabilities (e.g., enabling communication and/or collaboration withusers outside the platform), dashboard reports across subsets (e.g.,status reports of units of work associated with users within subsets),advanced search features, limiting access to units of work, advancedsupport resources, dependency capabilities (e.g., facilitating work unitdependencies such that a given unit of work may be dependent on anotherunit of work such that the other unit of work needs to be completedbefore the given unit of work can be started), onboarding resources(e.g., training materials, training sessions, etc.), premiumauthentication methods (e.g., SAML single sign on), unit of workcomments (e.g., project comments), premium views (e.g., a timeline view,a prioritization view, etc.) and/or other features.

In some implementations, premium features may include one or morecustomizable features. Customizable features may include one or morefeatures available to all users but customizable for users having firstlevel accounts. Customizable features may not be feasible for all usersacross an organization because one subset's customization may not berelevant and/or applicable for another subset. Having both group leveland subset level distinctions (within the user records) enablescustomizations for individual ones of the subsets, without applying suchcustomizations to the entire group (e.g., organization, etc.). Forexample, the customizable features may include one or more ofcustomizable status updates for units of work, customizablecommunication options, customizable work information fields,customizable dashboard views, customizable settings, privacy settingsfor subsets (e.g., subsets marked private), and/or other customizablefeatures.

In some implementations, users having first level accounts may interactand/or collaborate with users having second level accounts. In suchinstances, features component 112 may be configured to enable usershaving second level accounts to use one or more of the first levelfeatures while interacting and/or collaborating with the users that havefirst level accounts. For example, features component 112 may enable useof the first level feature by individual ones of the users in the secondsubset of users belonging to the overarching group but not belonging tothe first subset while individuals ones of the users within the firstsubset of users are engaging with the individual ones of the users inthe second subset of users. Use of the first level features may belimited and/or restricted to use for a specific unit of work,interaction, and/or collaboration between a user having a first levelaccount and a user having a second level account.

In some implementations, feature component 112 may be configured toprovide access to second level features within the collaboration workmanagement platform to the users belonging to the overarching group. Theusers belonging to the overarching group, including the users that havefirst level accounts, second level accounts, and/or other level accounts(but belong to the overarching group). Second level features may includestandard platform features including but not limited to: work unitgeneration, assignment of units of work, communication, attachments forunits of work, status updates, activity feed, various views of one ormore units of work associated with the user, work unit permissions, workunit workspaces, and/or other features.

In some implementations, server(s) 102, client computing platform(s)104, and/or external resources 116 may be operatively linked via one ormore electronic communication links. For example, such electroniccommunication links may be established, at least in part, via a networksuch as the Internet and/or other networks. It will be appreciated thatthis is not intended to be limiting, and that the scope of thisdisclosure includes implementations in which server(s) 102, clientcomputing platform(s) 104, and/or external resources 116 may beoperatively linked via some other communication media.

A given client computing platform 104 may include one or more processorsconfigured to execute computer program components. The computer programcomponents may be configured to enable an expert and/or user associatedwith the given client computing platform 104 to interface with system100 and/or external resources 116, and/or provide other functionalityattributed herein to client computing platform(s) 104. By way ofnon-limiting example, the given client computing platform 104 mayinclude one or more of a desktop computer, a laptop computer, a handheldcomputer, a tablet computing platform, a NetBook, a Smartphone, a gamingconsole, and/or other computing platforms.

External resources 116 may include sources of information outside ofsystem 100, external entities participating with system 100, and/orother resources. In some implementations, some and/or all of thefunctionality attributed herein to external resources 116 may beprovided by resources included in system 100.

Server(s) 102 may include electronic storage 118, one or more processors120, and/or other components. Server(s) 102 may include communicationlines, and/or ports to enable the exchange of information with a networkand/or other computing platforms. Illustration of server(s) 102 in FIG.1 is not intended to be limiting. Server(s) 102 may include a pluralityof hardware, software, and/or firmware components operating together toprovide the functionality attributed herein to server(s) 102. Forexample, server(s) 102 may be implemented by a cloud of computingplatforms operating together as server(s) 102.

Electronic storage 118 may comprise non-transitory storage media thatelectronically stores information. The electronic storage media ofelectronic storage 118 may include one and/or both of system storagethat is provided integrally (i.e., substantially non-removable) withserver(s) 102 and/or removable storage that is removably connectable toserver(s) 102 via, for example, a port (e.g., a USB port, a firewireport, etc.) and/or a drive (e.g., a disk drive, etc.). Electronicstorage 118 may include one or more of optically readable storage media(e.g., optical disks, etc.), magnetically readable storage media (e.g.,magnetic tape, magnetic hard drive, floppy drive, etc.), electricalcharge-based storage media (e.g., EEPROM, RAM, etc.), solid-statestorage media (e.g., flash drive, etc.), and/or other electronicallyreadable storage media. Electronic storage 118 may include one or morevirtual storage resources (e.g., cloud storage, a virtual privatenetwork, and/or other virtual storage resources). Electronic storage 118may store software algorithms, information determined by processor(s)120, information received from server(s) 102, information received fromclient computing platform(s) 104, and/or other information that enablesserver(s) 102 to function as described herein.

Processor(s) 120 may be configured to provide information processingcapabilities in server(s) 102. As such, processor(s) 120 may include oneor more of a digital processor, an analog processor, a digital circuitdesigned to process information, an analog circuit designed to processinformation, a state machine, and/or other mechanisms for electronicallyprocessing information. Although processor(s) 120 is shown in FIG. 1 asa single entity, this is for illustrative purposes only. In someimplementations, processor(s) 120 may include a plurality of processingunits. These processing units may be physically located within the samedevice, and/or processor(s) 120 may represent processing functionalityof a plurality of devices operating in coordination. Processor(s) 120may be configured to execute components 108, 110, 112, and/or othercomponents. Processor(s) 120 may be configured to execute components108, 110, 112, and/or other components by software; hardware; firmware;some combination of software, hardware, and/or firmware; and/or othermechanisms for configuring processing capabilities on processor(s) 120.As used herein, the term “component” may refer to any component and/orset of components that perform the functionality attributed to thecomponent. This may include one or more physical processors duringexecution of processor readable instructions, the processor readableinstructions, circuitry, hardware, storage media, and/or any othercomponents.

It should be appreciated that although components 108, 110, and 112 areillustrated in FIG. 1 as being implemented within a single processingunit, in implementations in which processor(s) 120 includes multipleprocessing units, one or more of components 108, 110, and/or 112 may beimplemented remotely from the other components. The description of thefunctionality provided by the different components 108, 110, and/or 112described below is for illustrative purposes, and is not intended to belimiting, as any of components 108, 110, and/or 112 may provide moreand/or less functionality than is described. For example, one or more ofcomponents 108, 110, and/or 112 may be eliminated, and some and/or allof its functionality may be provided by other ones of components 108,110, and/or 112. As another example, processor(s) 120 may be configuredto execute one or more additional components that may perform someand/or all of the functionality attributed below to one of components108, 110, and/or 112.

FIG. 3 illustrates a method 300 for providing a collaboration workmanagement platform that facilitates differentiation between users in anoverarching group and one or more subsets of individual users within theoverarching group to enable the users within the individual subsets touse the collaboration work management platform differently users withinthe other subsets, the method being implemented by a computer systemincluding one or more physical processors configured by machine-readableinstructions, in accordance with one or more implementations. Theoperations of method 300 presented below are intended to beillustrative. In some implementations, method 300 may be accomplishedwith one or more additional operations not described, and/or without oneor more of the operations discussed. Additionally, the order in whichthe operations of method 300 are illustrated in FIG. 3 and describedbelow is not intended to be limiting.

In some implementations, method 300 may be implemented in one or moreprocessing devices (e.g., a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, and/or othermechanisms for electronically processing information). The one or moreprocessing devices may include one or more devices executing some and/orall of the operations of method 300 in response to instructions storedelectronically on an electronic storage medium. The one or moreprocessing devices may include one or more devices configured throughhardware, firmware, and/or software to be specifically designed forexecution of one or more of the operations of method 300.

An operation 302 may include managing environment state information formaintaining a collaboration environment. The environment stateinformation may include user records and work unit records. Theenvironment state information may define a state of the collaborationenvironment including a user state and a work unit state. The user statemay be defined by the user records that define values of user parametersassociated with users interacting with and/or viewing the collaborationenvironment. The work unit state may be defined by the work unit recordsthat define values of work unit parameters for units of work managed,created, and/or assigned within the collaboration environment. The userparameters may include a group parameter identifying the overarchinggroup to which a first set of users, including a first user, belong. Assuch, a first user record for the first user may define a first groupvalue of the group parameter indicating the overarching group. The userparameters may include a subset parameter denoting one or more subsetswithin an overarching group to which one or more users within the firstset of users belongs. As such, the first user record for the first usermay define a first subset value of the subset parameter indicating afirst subset within the overarching group to which a first subset ofusers, including the first user, belong. Operation 302 may be performedby one or more hardware processors configured by machine-readableinstructions including a component that is the same as and/or similar tocollaboration environment component 108, in accordance with one or moreimplementations.

An operation 304 may include effectuating presentation of thecollaboration environment for the collaboration work management platformbased on the environment state information including the user recordsand the work unit records. Operation 304 may be performed by one or morehardware processors configured by machine-readable instructionsincluding a component that is the same as and/or similar to presentationcomponent 110, in accordance with one or more implementations.

FIG. 4 illustrates a method 400 for providing a collaboration workmanagement platform that facilitates differentiation between users in anoverarching group and one or more subsets of individual users within theoverarching group to enable the users within the individual subsets touse the collaboration work management platform differently users withinthe other subsets, the method being implemented by a computer systemincluding one or more physical processors configured by machine-readableinstructions, in accordance with one or more implementations. Theoperations of method 400 presented below are intended to beillustrative. In some implementations, method 400 may be accomplishedwith one or more additional operations not described, and/or without oneor more of the operations discussed. Additionally, the order in whichthe operations of method 400 are illustrated in FIG. 4 and describedbelow is not intended to be limiting.

In some implementations, method 400 may be implemented in one or moreprocessing devices (e.g., a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, and/or othermechanisms for electronically processing information). The one or moreprocessing devices may include one or more devices executing some and/orall of the operations of method 400 in response to instructions storedelectronically on an electronic storage medium. The one or moreprocessing devices may include one or more devices configured throughhardware, firmware, and/or software to be specifically designed forexecution of one or more of the operations of method 400.

An operation 402 may include managing environment state information formaintaining a collaboration environment. The environment stateinformation may include user records and work unit records. Theenvironment state information may define a state of the collaborationenvironment including a user state and a work unit state. The user statemay be defined by the user records that define values of user parametersassociated with users interacting with and/or viewing the collaborationenvironment. The work unit state may be defined by the work unit recordsthat define values of work unit parameters for units of work managed,created, and/or assigned within the collaboration environment. The userparameters may include a group parameter identifying the overarchinggroup to which a first set of users, including a first user, belong. Assuch, a first user record for the first user may define a first groupvalue of the group parameter indicating the overarching group. The userparameters may include a subset parameter denoting one or more subsetswithin an overarching group to which one or more users within the firstset of users belongs. As such, the first user record for the first usermay define a first subset value of the subset parameter indicating afirst subset within the overarching group to which a first subset ofusers, including the first user, belong. Operation 402 may be performedby one or more hardware processors configured by machine-readableinstructions including a component that is the same as and/or similar tocollaboration environment component 108, in accordance with one or moreimplementations.

An operation 404 may include effectuating presentation of thecollaboration environment for the collaboration work management platformbased on the environment state information including the user recordsand the work unit records. Operation 404 may be performed by one or morehardware processors configured by machine-readable instructionsincluding a component that is the same as and/or similar to presentationcomponent 110, in accordance with one or more implementations.

An operation 406 may include providing and/or restricting access tofirst level features for the users within the collaboration workmanagement platform based on whether or not the users belong to both theoverarching group and the first subset of users. Operation 406 may beperformed by one or more hardware processors configured bymachine-readable instructions including a component that is the same asand/or similar to presentation component 110, in accordance with one ormore implementations.

Although the present technology has been described in detail for thepurpose of illustration based on what is currently considered to be themost practical and preferred implementations, it is to be understoodthat such detail is solely for that purpose and that the technology isnot limited to the disclosed implementations, but, on the contrary, isintended to cover modifications and equivalent arrangements that arewithin the spirit and scope of the appended claims. For example, it isto be understood that the present technology contemplates that, to theextent possible, one or more features of any implementation can becombined with one or more features of any other implementation.

What is claimed is:
 1. A system configured to temporarily enablefeatures within an online collaboration environment, the systemcomprising: one or more hardware processors configured bymachine-readable instructions to: enable use of a first feature by afirst user while the first user is collaborating with a second userwithin an online collaboration environment, the first user belonging toa first subset of users but not belonging to a second subset of users,the second user belonging to the second subset of users; and disable theuse of the first feature by the first user when the first user is nolonger collaborating with the second user within the onlinecollaboration environment.
 2. The system of claim 1, wherein the one ormore hardware processors configured by the machine-readable instructionsto: manage user information associated with the first user and thesecond user, the user information identifying an overarching group ofthe first user and the second user.
 3. The system of claim 1, whereinthe first subset of users has an account level that is different fromthe second subset of users.
 4. The system of claim 3, wherein theaccount level of the first subset of users does not provide access tothe first feature.
 5. The system of claim 4, wherein another accountlevel of the second subset of users is associated with access to thefirst feature.
 6. The system of claim 1, wherein the first feature isone or more of use of custom work unit template, an external invitecapability, use of a dashboard report, a search feature, access to workunits, access to a support resource, a dependency capability, or accessto onboarding resources.
 7. The system of claim 2, wherein theoverarching group includes one or more of an organization, a company, anentity, a corporation, an enterprise, or a business.
 8. The system ofclaim 7, wherein the first subset of users includes one or more of asub-group, a division, a department, or a task force within theoverarching group.
 9. The system of claim 1, wherein the one or morehardware processors configured by machine-readable instructions todetermine when the first user is collaborating with the second user bydetermining if the first user and the second user are working on aspecific unit of work within the online collaboration environment. 10.The system of claim 1, wherein the one or more hardware processorsconfigured by machine-readable instructions to determine when the firstuser is collaborating with the second user by determining if the firstuser and/or the second user are performing a specific interaction withinthe online collaboration environment.
 11. A method to temporarily enablefeatures within an online collaboration environment, the systemcomprising: enabling use of a first feature by a first user while thefirst user is collaborating with a second user within an onlinecollaboration environment, the first user belonging to a first subset ofusers but not belonging to a second subset of users, the second userbelonging to the second subset of users; and disabling the use of thefirst feature by the first user when the first user is no longercollaborating with the second user within the online collaborationenvironment.
 12. The method of claim 11, further comprising: obtaininguser information associated with the first user and the second user, theuser information identifying an overarching group of the first user andthe second user.
 13. The method of claim 11, wherein the first subset ofusers has an account level that is different from the second subset ofusers.
 14. The method of claim 13, wherein the account level of thefirst subset of users does not provide access to the first feature. 15.The method of claim 14, wherein another account level of the secondsubset of users is associated with access to the first feature.
 16. Themethod of claim 11, wherein the first feature is one or more of use ofcustom work unit template, an external invite capability, use of adashboard report, a search feature, access to work units, access to asupport resource, a dependency capability, or access to onboardingresources.
 17. The method of claim 12, wherein the overarching groupincludes one or more of an organization, a company, an entity, acorporation, an enterprise, or a business.
 18. The method of claim 17,wherein the first subset of users includes one or more of a sub-group, adivision, a department, or a task force within the overarching group.19. The method of claim 11, further comprising determining when thefirst user is collaborating with the second user by determining if thefirst user and the second user are working on a specific unit of workwithin the online collaboration environment.
 20. The method of claim 11,further comprising determining when the first user is collaborating withthe second user by determining if the first user and/or the second userare performing a specific interaction within the online collaborationenvironment.